-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow BYO auth backend #269
base: master
Are you sure you want to change the base?
Conversation
This PR has been marked as stale because it has been open for 30 days with no activity. Are there any blockers, or should this be closed? |
Still relevant - I want to merge this in. Just need to think about what to do with the logout endpoint. |
yup, I'm not sure either. Maybe just allow pointing to a custom logout url? If this was setup using oauth proxy or similar, we'd send the user to the auth0 logout url (which is known) for the auth0 app that is used with oauth proxy. Most auth providers supply a logout url, so having that as an optional parameter would imho make sense. |
This PR has been marked as stale because it has been open for 30 days with no activity. Are there any blockers, or should this be closed? |
I'm also interested in getting something like this included |
This PR has been marked as stale because it has been open for 30 days with no activity. Are there any blockers, or should this be closed? |
Allows replacing the built-in auth backend with a custom one.
This allowed me to do:
It would be cool if it was somehow possible to override the default "non-authenticated" behavior, and for example have admin-api redirect the user to another login url instead of the built-in one, but I didn't find a clean way to do that.